From: Florian Müllner <fmuellner@gnome.org>
Date: Thu, 8 Apr 2021 15:31:54 +0000 (+0200)
Subject: workspacesView: Don't tie PgUp/PgDown to mapped state
X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~616^2^2~69
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=dd7d33622875c70f3f5965f387e4de7c99fbf330;p=gnome-shell.git

workspacesView: Don't tie PgUp/PgDown to mapped state

Both app grid and window picker are now always visible in the overview,
so their handling of the PgUp/PgDown keys conflicts.

Resolve that by checking for the overview state instead.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1798>
---

diff --git a/js/ui/workspacesView.js b/js/ui/workspacesView.js
index 2c9da5c9b..502590418 100644
--- a/js/ui/workspacesView.js
+++ b/js/ui/workspacesView.js
@@ -1142,7 +1142,8 @@ class WorkspacesDisplay extends St.Widget {
     }
 
     _onKeyPressEvent(actor, event) {
-        if (!this.mapped)
+        const { ControlsState } = OverviewControls;
+        if (this._overviewAdjustment.value !== ControlsState.WINDOW_PICKER)
             return Clutter.EVENT_PROPAGATE;
 
         const { workspaceManager } = global;